private-key-cron-21: sample cronjob #60
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Honestly I think the use of Cron here could lead to a race condition and potential corruption of the config as a whole so it's probably best avoided. |
|
Looking at the code and placing a defer on the add profile to not store the private key after download is probably best. So as part of the add device they automatically get the file downloaded then clean up the key what's your thoughts on this ? |
Author
|
@gavinelder I'm running this at the moment no problem. You could change it to a find command so it never touches new files but I didn't think it was worth it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Basic mitigation for storing the private keys on the server. Referenced in this ticket:-
#21